Performance Graph View
The Performance Graph view contains counters graphs of: gDEBugger, operating system, and vendor specific graphic boards (NVIDIA and 3DLabs currently). For example: CPU/GPU idle, graphic memory consumption, vertex and fragment processors utilizations, number of function calls per frame, frame per second, etc...
Graph View:
The Graph view displays counter values as continuous line graphs. You can select the color and line width for each line graph to distinguish it from the other graphs. Data samples are added at the graph's right side, pushing old samples left. Use the Graph view scroll bar to view old data samples that have been pushed out of the current graph view.
gDEBugger queries and reports the performance counters periodically. (Every 500 milliseconds by default). The elapsed time, measured in seconds, from the debugged application launch time is displayed as the scroll bar maximal (right) value.
The performance graph logged data can be saved in a file (.csv) from the Performance Analysis toolbar or from the file menu.
List View:
The List view displays the name, the latest sampled value and the latest scaled value (latest sampled value multiplied by the scale factor) of each performance counter. The font color of the counter name is the same as the line in the Graph view. Selecting a counter highlights the selected graph in the Graph view.
Double clicking on an item opens the Performance Counters dialog where you can add new counters and set the attributes of each counter.
Available Counter Type Icons:
- A gDEBugger performance counter.
- A 3Dlabs performance counter.
- An NVIDIA performance counter.
- A Win32 performance counter.
Saving Performance Data Counters in a File
The performance data can be saved in a file (.csv) from the Performance Analysis toolbar or from the File menu. Saving performance data in a file enables you to compare performance tests for your application using different hardware and driver configurations or to perform regression tests (compare the performance of two versions of your application).
Performance Tip:
The gDEBugger Performance Analysis toolbar enables you to pinpoint application performance bottlenecks quickly and easily. The toolbar contains commands which allow you to disable stages of the graphics pipeline one by one. These commands include: eliminate all OpenGL draw commands, force single pixel view port, render using no lights, force 2x2 stub textures and force a stub fragment shader. If the performance metrics improves when a certain stage has been turned off, then you have found a graphics pipeline bottleneck!
gDEBugger User Guide